Forem: Jay Jethava

Avoid Bugs in Your Code: Mutating vs. Non-Mutating Methods in Moment.js

Jay Jethava — Fri, 13 Sep 2024 11:52:04 +0000

When working with Moment.js, it’s essential to know which methods change the original date object and which return new values. This can help you avoid unintended side effects in your code. Here’s a quick guide:

🔄Methods that Mutate the Original Date Object:

startOf(unit) — Sets the date to the start of the specified unit (e.g., ‘year’, ‘month’, ‘day’).
endOf(unit) — Sets the date to the end of the specified unit.
add(value, unit) — Adds time to the original Moment object based on the specified value and unit.
subtract(value, unit) — Subtracts time from the original Moment object based on the specified value and unit.
set(unit, value) — Sets the specified unit of the original Moment object to the given value.

🆕 Methods that Return a New Object:

toISOString() — Converts the Moment object to an ISO 8601 string.
toDate() — Converts the Moment object to a native JavaScript Date object.
format() — Formats the Moment object as a string based on the provided • format string.
clone() — Creates a copy of the Moment object.

Knowing the difference between mutating and non-mutating methods in Moment.js is crucial for writing clean and predictable code. Be mindful of these distinctions to avoid unexpected bugs and improve code maintainability.

Avoid Bugs in Your Code: Mutating vs. Non-Mutating Methods in Moment.js

Jay Jethava — Fri, 13 Sep 2024 11:52:04 +0000

🔄Methods that Mutate the Original Date Object:

startOf(unit) — Sets the date to the start of the specified unit (e.g., ‘year’, ‘month’, ‘day’).
endOf(unit) — Sets the date to the end of the specified unit.
add(value, unit) — Adds time to the original Moment object based on the specified value and unit.
subtract(value, unit) — Subtracts time from the original Moment object based on the specified value and unit.
set(unit, value) — Sets the specified unit of the original Moment object to the given value.

🆕 Methods that Return a New Object:

toISOString() — Converts the Moment object to an ISO 8601 string.
toDate() — Converts the Moment object to a native JavaScript Date object.
format() — Formats the Moment object as a string based on the provided • format string.
clone() — Creates a copy of the Moment object.

Avoid Bugs in Your Code: Mutating vs. Non-Mutating Methods in Moment.js

Jay Jethava — Fri, 13 Sep 2024 11:52:04 +0000

🔄 Methods that Mutate the Original Date Object

startOf(unit) — Sets the date to the start of the specified unit (e.g., ‘year’, ‘month’, ‘day’).
endOf(unit) — Sets the date to the end of the specified unit.
add(value, unit) — Adds time to the original Moment object based on the specified value and unit.
subtract(value, unit) — Subtracts time from the original Moment object based on the specified value and unit.
set(unit, value) — Sets the specified unit of the original Moment object to the given value.

🆕 Methods that Return a New Object:

toISOString() — Converts the Moment object to an ISO 8601 string.
toDate() — Converts the Moment object to a native JavaScript Date object.
format() — Formats the Moment object as a string based on the provided • format string.
clone() — Creates a copy of the Moment object.

𝗘𝗻𝗵𝗮𝗻𝗰𝗶𝗻𝗴 𝗔𝗣𝗜 𝗖𝗹𝗮𝗿𝗶𝘁𝘆: 𝗣𝗼𝘀𝘁𝗺𝗮𝗻 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗕𝗲𝘀𝘁 𝗣𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀

Jay Jethava — Fri, 06 Sep 2024 12:24:47 +0000

Today, I’m excited to share some of the steps I’ve taken to simplify the API workflows using Postman, bridging the gap between front-end and back-end teams for smoother collaboration.

𝗞𝗲𝘆 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀:

𝗔𝗶𝗺
• This outlines the primary purpose of the API endpoint.
• This helps developers to understand the specific functionality that the endpoint provides, ensuring that they use it correctly in their applications.
𝗔𝗰𝗰𝗲𝘀𝘀
• This specifies “who is authorised to make requests to this endpoint?”.
• This helps developers to avoid unnecessary errors or access issues during integration by clarifying the security requirements.
𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻
• This explains how the API endpoint is integrated within the front end.
• This details the specific front-end components or pages that rely on this endpoint.
• This helps developers to easily debug issues and make changes without disrupting other parts of the application.
𝗣𝗮𝘆𝗹𝗼𝗮𝗱
• If the API is accepting some data in the body/payload then save an example of the payload.
• This helps developers see exactly what data format and structure they need to provide, ensuring proper API calls.

By focusing on these essential elements, I ensure the API documentation is not just informative but also practical, enhancing productivity and reducing integration and debugging time.