radashi-org radashi Rfcs Discussions
Pinned Discussions
RFCs Discussions
Proposals that need community feedback
Pinned to RFCs
-
You must be logged in to vote Naming conventions
philosophyThis issue/discussion is about Radashi's design philosophy.
Discussions
-
You must be logged in to vote Deprecate
stage 0: proposedguardA proposal for a change that is offered for community and team evaluation. -
You must be logged in to vote Align
BREAKING CHANGEAggregateErrorpolyfill with specificationNot backwards compatible -
You must be logged in to vote Make
BREAKING CHANGEisNumberreturn true for NaNNot backwards compatible stage 2: in developmentAn RFC that's being implemented or is in review. -
You must be logged in to vote Deprecate
future planninggroupeventuallyThere's no intention to resolve this in the near-term. -
You must be logged in to vote Deprecate
future planningflateventuallyThere's no intention to resolve this in the near-term. -
You must be logged in to vote Change
BREAKING CHANGErangemax parameter to be exclusiveNot backwards compatible stage 0: proposedA proposal for a change that is offered for community and team evaluation. -
You must be logged in to vote Allowing undefined as the NaN fallback in
BREAKING CHANGEtoIntandtoFloatNot backwards compatible stage 0: proposedA proposal for a change that is offered for community and team evaluation. -
You must be logged in to vote Rename
BREAKING CHANGEisPromisetoisPromiseLikeorisThenableNot backwards compatible stage 1: acceptedAn RFC waiting for someone to implement it. -
You must be logged in to vote Consider renaming
BREAKING CHANGEshiftNot backwards compatible stage 2: in developmentAn RFC that's being implemented or is in review. -
You must be logged in to vote Publish sub-packages to NPM
stage 0: proposedA proposal for a change that is offered for community and team evaluation. -
You must be logged in to vote Move type exports to
BREAKING CHANGEradashi/typesmodule.Not backwards compatible stage 1: acceptedAn RFC waiting for someone to implement it. -
You must be logged in to vote -
You must be logged in to vote Rework type guards in Radashi
BREAKING CHANGENot backwards compatible stage 0: proposedA proposal for a change that is offered for community and team evaluation. -
You must be logged in to vote Remove
BREAKING CHANGEisFloatNot backwards compatible stage 0: proposedA proposal for a change that is offered for community and team evaluation. -
You must be logged in to vote Rename
BREAKING CHANGEassigntoassignDeepNot backwards compatible stage 1: acceptedAn RFC waiting for someone to implement it. -
You must be logged in to vote Deprecate
future planningdeferwhen theusingkeyword becomes widely availableThere's no intention to resolve this in the near-term. stage 1: acceptedAn RFC waiting for someone to implement it. -
You must be logged in to vote Align
BREAKING CHANGEcapitalizewith the built-inCapitalize<T>TypeScript typeNot backwards compatible stage 1: acceptedAn RFC waiting for someone to implement it. -
You must be logged in to vote Rename the
BREAKING CHANGEdrawfunctionNot backwards compatible stage 0: proposedA proposal for a change that is offered for community and team evaluation. -
You must be logged in to vote Remove default size of
BREAKING CHANGEclusterNot backwards compatible stage 1: acceptedAn RFC waiting for someone to implement it. -
You must be logged in to vote Add
help wantedselectEntriesas amapEntriesthat can also filter out entriesExtra attention is needed good first issueGood for newcomers -
You must be logged in to vote Change
BREAKING CHANGEtrimto require its 2nd argumentNot backwards compatible stage 1: acceptedAn RFC waiting for someone to implement it. -
You must be logged in to vote Remove undefined input checks from all functions
BREAKING CHANGENot backwards compatible stage 2: in developmentAn RFC that's being implemented or is in review.
