Project

General

Profile

Actions

Task #323

closed

Routes issues

Added by Filip Měšťánek about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
High
Assignee:
Radek Tomiška
Category:
Frontend
Target version:
Start date:
03/01/2017
Due date:
% Done:

100%

Estimated time:
Owner:

Description

During development of new module I couldn't get custom routes to work. I set up paths in the 'routes.js' file but when I tried to access the pages, I got 404. After a bit of playing we found out, that if we change name of the module to a name alphabetically before 'core' ('abc'), it is suddenly working.

Therefore we assume the module routes are processed in alphabetic order and because the core module has at the end a path with '*', no other path after that is working.


Related issues

Related to IdStory Identity Manager - Task #253: FE - load backend configuration before react router is inicializedClosedRadek Tomiška12/21/2016

Actions
Actions #1

Updated by Radek Tomiška about 7 years ago

  • Category set to Frontend
  • Status changed from New to Needs feedback
  • Assignee set to Ondřej Kopr
  • Target version set to Citrine (7.3.0)
  • % Done changed from 0 to 90

It was fixed by #253.

Could you make a test please?

Actions #2

Updated by Radek Tomiška about 7 years ago

  • Related to Task #253: FE - load backend configuration before react router is inicialized added
Actions #3

Updated by Ondřej Kopr about 7 years ago

  • Status changed from Needs feedback to Resolved
  • Assignee changed from Ondřej Kopr to Radek Tomiška
  • % Done changed from 90 to 100

Feedback in #253

Actions #4

Updated by Radek Tomiška about 7 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF