React Redux Online Test

Finish the FocusableInput component so that the input element automatically receives focus on the first render if the shouldFocus prop is true.

 Consider the following Redux reducer defined to manage a wish list:

const wishListReducer = createReducer(initialState, (builder) => {
  builder
    .addCase(removeItem, (state, action) => {
      state.wishList = state.wishList.filter((item => item !== action.payload))
    })
    .addCase(addItem, (state, action) => {
      if(state.wishList.length < 10) {
        state.wishList.push(action.payload)
      }
    })    
    .addDefaultCase((state, action) => {});
});

const store = configureStore({
  reducer: {
    cart: wishListReducer,
  },
});

The initial wish list:

const initialState = {
  wishList: [
    "Toy Car",
    "Football"
  ],
};

Considering the initalState and wishListReducer defined above, what is true about wishListReducer?

An RPG game lets you assign points to various attributes of your character to improve it. The points earned by the character are available to assign across all attributes. Each attribute can only be assigned at most 70% of totalPoints (rounded down to the nearest integer) unless totalPoints is 1, in which case only one attribute can get a maximum of 1 point. The sum of all points assigned plus the points remaining should add up to totalPoints.

Implement the CharacterAttributes component with the logic described above and the following requirements:

• Points should be assigned by moving the slider and the remaining points should be displayed in the span tag.
• When initialized, all points are available and all sliders start at 0.
• Each slider must have a range from 0 up to totalPoints.

For example, if totalPoints is 15 then the user shouldn't be able to drag the slider past 10 even if more points are available.

Write a TodoList component that expects an items prop which is a list of objects, each with text and done properties.

TodoList also accepts an onItemClick function prop, which should be called when a user clicks an item in the list, if the item is not marked as done. Otherwise, the onItemClick should not be called and the click event itself should not be propagated further. The function should be called with the item object from the items list as the first parameter and the event as the second parameter.

The Message component contains an anchor element and a paragraph below the anchor. Rendering of the paragraph should be toggled by clicking on the anchor element using the following logic:

• At the start, the paragraph should not be rendered.
• After a click, the paragraph should be rendered.
• After another click, the paragraph should not be rendered.

Finish the Message component by implementing this logic.

An image gallery is a set of images with corresponding remove buttons. This is the HTML code for a gallery with two images:

<div>
  <div class="image">
    <img src="https://bit.ly/3xXPxPR">
    <button class="remove">X</button>
  </div>
  <div class="image">
    <img src="https://bit.ly/4de3sQr">
    <button class="remove">X</button>
  </div>
</div>

Implement the ImageGallery component that accepts a links prop and renders the gallery described above so that the first item in the links prop is the src attribute of the first image in the gallery. It should also implement the following logic: When the button is clicked, the image that is in the same div as the button should be removed from the gallery.

For example, after the first image has been removed from the gallery above, it's HTML code should look like this:

<div>
  <div class="image">
    <img src="https://bit.ly/4de3sQr">
    <button class="remove">X</button>
  </div>
</div>

This application should allow the user to update their username by inputting a custom value and clicking the button.

The Username component is finished and should not be changed, but the App component is missing parts. Finish the App component so that the Username component displays the inputted text when the button is clicked.

For example, if the user inputs a new username of "John Doe" and clicks the button, App's div element should look like this:

<div><button>Change Username</button><input type="text"><h1>John Doe</h1></div>

There might be multiple App elements on the page.

You have a GroceryApp component, which receives a list of products, each one with name and votes. The app should render an unordered list, with a list item for each product. Products can be upvoted or downvoted.

By appropriately using React state and props, implement the upvote/downvote logic. Keep the state in the topmost component, while the Product component should accept props.

For example, passing the following array as products prop to GroceryApp [{ name: "Oranges", votes: 0 }, { name: "Bananas", votes: 0 }] and clicking the '+' button next to the Oranges should result in HTML like:

<div id="root">
  <ul>
    <li>
      <span>Oranges</span> - <span>votes: 1</span><button>+</button> <button>-</button>
    </li>
    <li>
      <span>Bananas</span> - <span>votes: 0</span><button>+</button> <button>-</button>
    </li>
  </ul>
</div>

The TextInput component renders an input element in the DOM and accepts a ref that is forwarded to that input element. Finish the FocusableInput component:

• The component should accept a focused prop.
• When the focused prop is changed from false to true, and the input is not focused, it should receive the focus.
• If on mounting the focused prop is true, the input should receive the focus.

Consider the following React components:

const SecurityContext = React.createContext({ username: "", permissions: [] });

const ControlsComponent = (props) => {
  return (
    <SecurityContext.Provider value={{ username: props.username }}>
      <LogoutWrapper></LogoutWrapper>
    </SecurityContext.Provider>
  );
};

const LogoutWrapper = (props) => {
  var context = React.useContext(SecurityContext);
  
  return (
    <div>
      <p>{context.username}</p>
      <button>Click here to logout</button>
    </div>
  );
};

Select all the correct statements if ControlsComponent is rendered with the username prop equal to "James".

A web application for a meteorologist's dashboard uses a Redux store to manage temperature data. The Redux store is configured with the Redux toolkit where the latest temperature data is fetched using the Redux thunk function.

Below is the code for the store's configuration:

const weatherURL = "http://example.com/temperaturejson";

const fetchTemperature = createAsyncThunk(
  "weather/fetchTemperature",
  async (arg, thunkAPI) => {
    const response = await fetch(weatherURL);
    return response.json();
  }
);

const temperatureSlice = createSlice({
  name: "temperature",
  initialState: { temperature: 0 },
  reducers: {},
  extraReducers: (builder) => {
    builder.addCase(fetchTemperature.fulfilled, (state, action) => {
      state.temperature = action.payload.temperature;
    });
    builder.addCase(fetchTemperature.pending, (state, action) => {
      state.temperature = "loading";
    });
    builder.addCase(fetchTemperature.rejected, (state, action) => {
      console.log(action);
      state.temperature = "unavailable";
    });
  },
});

const weatherStore = configureStore({ reducer: temperatureSlice.reducer });

What is true about the behavior of weatherStore?