Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

♻️ 161 - replace freactal #168

Open
wants to merge 62 commits into
base: develop
Choose a base branch
from
Open

Conversation

anncatton
Copy link
Contributor

@anncatton anncatton commented May 1, 2021

Removes freactal dependency.
Replaces freactal stateProviders with context providers.
Adds jwt validation. Force logout on expired token.
Disable button calls patch update immediately, no staging changes + save
Small modification to sort behaviour, offset will not reset to 0 when sort direction/field is changed

Base automatically changed from feature/upgrade-cra to develop May 10, 2021 14:40
joneubank
joneubank previously approved these changes May 27, 2021
Copy link
Contributor

@joneubank joneubank left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So much good work here. Thanks for cleaning up all the type names as well. Couple places where commented code can be cleaned up, otherwise is good to go.

}),
);
const enhance = compose();
// defaultProps({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove unused code comments

}) => {
stageChange,
} = useEntityContext();
// withState('items', 'setItems', ({ associatedItems }) => associatedItems),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove unused code comments

if (!egoJwt || !egoPublicKey) {
return false;
} else {
return jwt.verify(egoJwt, egoPublicKey, { algorithms: ['RS256'] }) && true;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why we have && true... if the intention is to force boolean return type, maybe we want !!jwt.verify(...)

export const isValidJwt = verifyJwt(EGO_PUBLIC_KEY);

export const decodeToken: (egoJwt?: string) => EgoJwtData | null = memoize((egoJwt) =>
egoJwt && isValidJwt(egoJwt) ? jwtDecode(egoJwt) : null,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

egoJwt && isn't necessary as this is checked in isValidJwt(egoJwt)

wip - initial table load with list provider
* Initialize entity context with id, reorganize providers

* load entity into context

* Add user meta components, common panel components

* rename panelcomponents

* Add fieldnames enum

* pr feedback
* Initialize entity context with id, reorganize providers

* load entity into context

* Add user meta components, common panel components

* Add fieldnames enum

* add group meta comp

* add policy and application content panels
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants