Skip to content

dot routing doesn't work #11842

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

Closed
gyuho opened this issue Sep 22, 2016 · 3 comments
Closed

dot routing doesn't work #11842

gyuho opened this issue Sep 22, 2016 · 3 comments

Comments

@gyuho
Copy link

gyuho commented Sep 22, 2016

I'm submitting a ... (check one with "x")

[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

I have this simple routes

import { Routes, RouterModule } from '@angular/router';

import { DocComponent }  from './doc/v3.1/doc.component';

const appRoutes: Routes = [
    { path: 'doc', redirectTo: '/doc/v3.1', pathMatch: 'full' },
    { path: 'doc/v3.1', component: DocComponent }
];

export const routing = RouterModule.forRoot(appRoutes);

export const routedComponents = [
    DocComponent
];

And when I reload with /doc/v3.1, I get

Cannot GET /doc/v3.1

Expected behavior

No error.

Reproduction of the problem

When I remove dot (e.g. /doc/v31), it works.

What is the motivation / use case for changing the behavior?

I just want dot routing for documents with semantic version names.

Please tell us about your environment:

Ubuntu 16.04

  • Angular version: 2.0.0

  • Browser: [Chrome 53.0.2785.89]

  • Language: [TypeScript 2.0]

  • Node (for AoT issues): node --version = v6.6.0

@ericmartinezr
Copy link
Contributor

Related/dup #8249

@vsavkin
Copy link
Contributor

vsavkin commented Oct 4, 2016

Dup of #8249

@vsavkin vsavkin closed this as completed Oct 4, 2016
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants